Print

The latest release information about the E-mail Campaign Manager module.

Some of the issues described on this page contain internal reference numbers. You can use these reference numbers when communicating with Sitecore about a particular issue or feature.

1.  Release History

August 5, 2011

E-mail Campaign Manager v1.2.0 rev.110708 has been tested and verified with the Microsoft .NET Framework 4.0, which is now officially supported for use with ECM 1.2.

July 13, 2011

The E-mail Campaign Manager v1.2.0 rev.110708 is released.

Tested with Sitecore CMS 6.4.1 rev.110621.

Compatibility
This version of the module only runs on Sitecore 6.4.

Change log.

New features:

• Email delivery
  • Improved integration with the Sitecore App Center Email Delivery Service, which can be used to send large numbers of email messages reliably.
  • A built-in facility allowing users to test the connection to the configured e-mail server has been introduced. This replaces the Email Server Verification Testing tool.
• Performance and Optimization
  • Significant improvements have been made to the performance of the e-mail dispatch process, ensuring a significant number of e-mails can be sent in a short time as part of an email campaign.
  • An ECM performance tuning guide has been created, to help developers and administrators optimized e-mail dispatch performance.
  • An emulation mode has been introduced, which provides a means of testing campaign throughput by emulating an MTA. MTA emulation allows you to mimic the round trip time required to send an email from the ECM to an MTA.
• Other new features
  • Support has been added for browsers other than Internet Explorer. The following browsers are now supported:
    • Internet Explorer 8
    • Mozilla Firefox 3.6
    • Google Chrome 12
    • Safari 5.0.2
  • You are now able to add and track links to external websites in your email campaign messages. These external links are mapped to a redirect page on your website so that you can track when recipients click on these links.

Important changes

• The following settings have been added to the ECM configuration file, as part of new features:
  • MaxConnectionUnavailable - the period of time the module tries to restore an MTA connection before a dispatch is paused.
  • MaxSendingAttempts - the number of attempts to send a message.
  • CheckReceiverRights - specifies whether to check the Read right of a recipient for a target item during message generation.
  • MtaEmulation.Active - specifies whether the message sending process is emulated without actual message transmission via MTA.
  • MtaEmulation.MinSendTime - the minimum amount of time to emulate a single dispatch.
  • MtaEmulation.MaxSendTime  - the maximum amount of time to emulate a single dispatch.
  • MtaEmulation.FailProbability - the probability of a connection fail that should be used for the emulation.
  • SMTP.MaxConnections - the maximum number of concurrent open SMTP connections allowed.
  • SMTP.ConnectionExpiration - the period of time the module keeps an SMTP connection open.
• The following settings have new default values:
  • MaxGenerationThreads (new default value: Environment.ProcessorCount * 2)
• The Renderer URL setting used to configure dedicated servers in multisite environments was removed from the ECM configuration item as this is now set automatically.
• The module now uses the new Sitecore App Center 2.0 API. This has added functionality to interact with MTA email delivery servers, including richer and more accurate Delivery Status Notification statistics.

Issues fixed

• Performance and dispatch issues
  • An issue which caused performance issues when dispatching multiple email campaigns has been fixed. (340215)
  • An issue which caused message dispatching to pause for a period of time if all configured dispatch threads were not in use has been fixed. (341413)
  • The upper limit on mails sent during performance tests has been removed. (338826, 344186)
  • An issue which caused messages to fail to be sent if a subscriber has subscriber has comma in the username has been fixed. Additional special characters in the usernames have also been allowed. (347193)
  • The module now attempts to resend any failed messaged when a dispatch is resumed after having been paused. (344413)
• Message configuration issues
  • An issue which prevented tokens from being inserted in the Rich Text Editor, if they were preceded by any text or images has been fixed.(337966)
  • An issue which caused links to images which contain spaces paths not to work correctly has been fixed.( 343695)
  • An issue causing an error when attempting insert a user field in a message subject when using Internet Explorer 8 has been fixed. (343031)
  • An error causing the mail header and footer to be displayed in the online version of message the first time the message is published has been fixed. (343382)
  • An issue causing javascript errors in some cases when trying to paste a token to the subject line of a message (343693)
  • An issue causing incorrect tokens to be displayed in the message subject field of sent messages has been fixed (348263)
  • An issue sometimes causing incorrect emails to be used when trying to change a subscriber’s email and employing the requiresUniqueEmail="true" setting in the web.config has been fixed.
• Reporting & logging issues
  • An issue causing the number of delivered messages in a subject test to be reported incorrectly has been fixed. (344923)
  • An issue causing the dispatch of a message to be aborted if a subscriber has been disabled has been fixed. (343322)
  • Additional logging information has been included when users are skipped during the queuing phase of the dispatch process. Log information is added when users are not found, disabled, reach a maximum number of failed deliveries, or have invalid email addresses. (344185)
  • Additional logging information during the dispatch process has been added. Log information is now added which indicate the number of queued recipients and the dispatch duration. (344205)
• Other issues
  • An issue which causes send failures for messages in a Target Audience which has been serialized and moved to another solution and then deserialized. (343973)

December 15, 2010

The E-mail Campaign Manager v1.2.0 rev.101214 is released.

Tested with Sitecore CMS 6.4.0 rev.101124.

Compatibility
This version of the module only runs on Sitecore 6.4.

Change log.

New features:

• Support has been added for the Page Editor featured in Sitecore CMS 6.4. This has resulted in changes to the sample newsletter provided in the module. This can now be edited using the full functionality of the CMS 6.4 Page Editor.
• The new inline Rich Text Editor featured in Sitecore CMS 6.4 is now used in newsletter messages. (337774)
• You are now able to personalize the online versions of messages. An example of this is given in the Newsletter Message template, which shows a personalized page when you click the "Please click here to see the online version." link.

2.  Known issues

The list of known issues present in the latest version of the E-mail Campaign Manager module.

1. In Safari, ECM is not displayed correctly.
   Reference number: 347482.
   If you are using the Safari browser the Email Campaign Manager application is not displayed correctly, the first time a user opens the application.
   

2. Message subject testing cannot be performed.
   Message subject testing cannot be performed on the “HTML” and “Plain Text” email campaign message types.
   

3. The email sent to administrators when a dispatch has been aborted has an incorrect subject.
   The email sent to administrators when a dispatch has been aborted has an incorrect subject – it says “Dispatch process is complete”. In addition the Japanese version of this message does not show the status of the message.

4. Subscription confirmation/notification messages are not sent in Live mode (358144)
    
   Workaround:
   Download the file with the updated pages.
   1. Replace the /sitecore/ConfirmSubscription.html and /sitecore/Unsubscribe.html files with the files that you download (item filtering is disabled for ClientApi calls).
   2. Modify and build the Subscription Form code file (see an example in the Subscription Form.ascx.cs file that you download):
      a. Add the UpdateSubscriptions() method (see its implementation in the Subscription Form.ascx.cs file that you download).
      b. Replace the following line:
      string itemIDToRedirect = ClientApi.UpdateSubscriptions(ContextContact.Name, infoArray, confirmSubscription);
      with the line
      string itemIDToRedirect = this.UpdateSubscriptions(infoArray);